Event-based directory and contact management

ABSTRACT

Data sharing between a first user and a second user includes receiving a scan code from the first user; associating the scan code with a first profile of the first user; receiving, from a second user, an indication that the second user scanned the scan code; identifying, for the first user, the second user as a potential contact; sending, to the first user, a first request to share first user data with the second user; and receiving, from the first user, a response to the first request to share the first user data with the second user. Managing a directory of contacts includes creating the directory of contacts; receiving an event-based joining tag for the directory; adding a contact; and responsive to an event-based joining tag being active, adding the contact to the directory of contacts.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims priority to and the benefit of U.S. Provisional Application Patent Ser. No. 62/733,919, filed Sep. 20, 2018, and is a continuation-in-part of U.S. application patent Ser. No. 16/212,902, filed Dec. 7, 2018, which is a continuation-in-part of U.S. application Ser. No. 15/217,424, filed Jul. 22, 2016, now U.S. Pat. No. 10,171,985, which claims the benefit of U.S. Provisional Application Nos. 62/195,534, filed Jul. 22, 2015, and 62/234,246, filed Sep. 29, 2015, each of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates to electronic sharing of user data, managing user data of a network, and locating user devices for data exchange.

BACKGROUND

Network management of user data, such as user profile and contact information, can include storage of user information, and storing updates of user information. Social media networks provide platforms for users to post user information for other users to view on user devices.

SUMMARY

Disclosed herein are implementations of methods and systems for event-based directory and contact management.

A first aspect is a system for data sharing between a first user and a second user. The system includes a memory and a processor. The processor is configured to execute instructions stored in the memory to receive a scan code from a first device of the first user; store the scan code in a permanent storage as a stored scan code; associate the stored scan code with a first profile of the first user, the first profile comprising user data; receive, from a second device of the second user, an indication that the second user scanned the scan code, wherein the second user did not scan the stored scan code; identify, for the first user, the second user as a potential contact; send, to the first user, a first request to share first user data of the first user with the second user; and receive, from the first user, a response to the first request to share the first user data of the first user with the second user.

A second aspect is a system for managing a directory of contacts. The system includes a memory and a processor. The processor is configured to execute instructions stored in the memory to create the directory of contacts; receive an event-based joining tag for the directory of contacts; add a contact; determine whether the event-based joining tag is active; and responsive to the event-based joining tag being active, add the contact to the directory of contacts.

A third aspect is method for data sharing between a first user and a second user. The method includes receiving a scan code from a first device of the first user; storing the scan code in a permanent storage as a stored scan code; associating the stored scan code with a first profile of the first user, the first profile comprising user data; receiving, from a second device of the second user, an indication that the second user scanned the scan code, wherein the second user did not scan the stored scan code; identifying, for the first user, the second user as a potential contact; sending, to the first user, a first request to share first user data of the first user with the second user; receiving, from the first user, a response to the first request to share the first user data of the first user with the second user; and establishing the second user as a contact of the first user.

A fourth aspect is a method for managing a directory of contacts. The method includes creating the directory of contacts; receiving an event-based joining tag for the directory of contacts; adding a contact; determining whether the event-based joining tag is active; and responsive to the event-based joining tag being active, adding the contact to the directory of contacts.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention is best understood from the following detailed description when read in conjunction with the accompanying drawings. It is emphasized that, according to common practice, the various features of the drawings are not to-scale. On the contrary, the dimensions of the various features are arbitrarily expanded or reduced for clarity.

FIG. 1 is a diagram of an example of an apparatus used with event-based directory management in accordance with implementations of this disclosure.

FIG. 2 is a diagram of an example of a system used with event-based directory management in accordance with implementations of this disclosure.

FIG. 3 is a flowchart diagram of an example of a process for data sharing between devices of FIG. 2 based on relative proximity in accordance with the implementations of this disclosure.

FIG. 4 is a diagram of an example of a user interface for in accordance with implementations of this disclosure.

FIG. 5 is a diagram of an example of a user interface display for detecting contacts automatically in accordance with implementations of this disclosure.

FIG. 6 is a diagram of an example of a user interface display for selecting user data for data sharing in accordance with implementations of this disclosure.

FIG. 7 is a diagram of an example of a user interface display for identifying a potential contact based on location in accordance with implementations of this disclosure.

FIG. 8 is a diagram of an example of a user interface display for identifying a potential contact by scan code in accordance with implementations of this disclosure.

FIG. 9 is a diagram of an example of a user interface display for sharing user data by scan code in accordance with implementations of this disclosure.

FIG. 10 is a diagram of an example of a user interface display for selecting location data for data sharing in accordance with implementations of this disclosure.

FIG. 11 is a diagram of an example of a user interface display of user data of listed registered contacts in accordance with implementations of this disclosure.

FIG. 12 is a diagram of an example of a user interface display for changing data sharing in accordance with implementations of this disclosure.

FIG. 13 is a diagram of an example of a user interface display for following registered users in accordance with implementations of this disclosure.

FIG. 14 is a diagram of an example of a user interface display for following registered contacts in accordance with implementations of this disclosure.

FIG. 15 is a diagram of an example of a user interface display for creating a directory of contacts in accordance with implementations of this disclosure.

FIG. 16 is a diagram of an example of a user interface display for setting permissions for a directory of contacts in accordance with implementations of this disclosure.

FIG. 17 is a diagram of an example of a user interface display for setting directory joining criteria in accordance with implementations of this disclosure.

FIG. 18 is a diagram of an example of a user interface display for editing a directory of contacts in accordance with implementations of this disclosure.

FIG. 19 is a diagram of an example of a user interface display for listing requests associated with a directory of contacts in accordance with implementations of this disclosure.

FIG. 20 is a diagram of an example of a user interface display for joining a directory of contacts in accordance with implementations of this disclosure.

FIG. 21 is a diagram of an example of feedback messages when successfully joining a directory of contacts in accordance with implementations of this disclosure.

FIG. 22 is a diagram of an example of a feedback message when domain directory joining criteria are not matched in accordance with implementations of this disclosure.

FIG. 23 is a diagram of an example of requesting to join a directory of contacts that is already joined in accordance with implementations of this disclosure.

FIG. 24 is a diagram of an example of requests issued by and requests received by a user to join a directory of contacts in accordance with implementations of this disclosure.

FIG. 25 is a process for creating a directory of contacts in accordance with an implementation of this disclosure.

FIG. 26 is a process for joining a directory of contacts in accordance with an implementation of this disclosure.

FIG. 27 is an example of directories of contacts in accordance with implementations of this disclosure.

FIG. 28 is a process for creating a directory of contacts in accordance with an implementation of this disclosure.

FIG. 29 illustrates examples of user interfaces for setting an event-based joining tag in accordance with implementations of this disclosure.

FIG. 30 illustrates additional examples of user interfaces for setting an event-based joining tag in accordance with implementations of this disclosure.

FIG. 31 illustrates examples of machine-readable codes that can be used on event badges according to implementations of this disclosure.

FIG. 32 is a process for data sharing between a first user and a second user in accordance with an implementation of this disclosure.

FIGS. 33A-33B illustrate examples of receiving a scan code in accordance with an implementation of this disclosure.

FIG. 34 illustrates an example of scanning an event badge in accordance with an implementation of this disclosure.

DETAILED DESCRIPTION

Various aspects of this disclosure are now described with reference to the drawings. In the following description, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. It should be understood, however, that certain aspects of this disclosure may be practiced without these specific details, or with other methods, components, materials, etc. In other instances, well-known structures and devices are shown in block diagram form to facilitate describing one or more aspects.

The present disclosure presents processes and apparatuses for detecting the proximity of contacts relative to a user and sharing contact information between the user and one or more detected contacts. A user of the disclosed processes and apparatuses, including without limitation computer readable instructions executable by the processing unit of the electronic device present disclosure (collectively, the “application”; noting, however, that said term may also include further embodiments as may hereinafter be described or referenced), may receive contact and other information and data (collectively, “user data”) from detected contacts (i.e., other users) and send their own user data thereto based in part on the types of information each user elects to share, the nature of the relationship between the users, and the conditions under which any user data may be shared. Generally, each user may receive user data from and transmit user data to other users, for example, by way of a server in communication with each user device, thereby resulting in a real-time exchange of user data, subject to any limitations as may be imposed by each user.

The present disclosure also presents processes and apparatuses for creating and joining a two-way permission-based directory of contacts. The creator of the directory of contacts is referred to herein as the “administrator” or “administrator of the directory.” The administrator can set permissions for the directory of contacts. For example, the permissions can indicate whether the directory of contacts is public or private. A public directory of contacts can be discoverable by other users who may join the directory. A private directory, depending on the level of privacy, may not discoverable. Whether discoverable or not, for a user to successfully join a private directory of contacts, one or more additional criteria of the permission may need to be satisfied as described below in illustrative examples.

Depending on the settings of a directory, the directory of contacts can be a two-way permission-based directory. A request from an administrator to a user (i.e., an invitee) to join a directory, may have to be accepted by the user before the user is added to the directory. A request to join a directory, initiated by a user and sent to the administrator of the directory, may have to be accepted by the administrator before the user is added to the directory. As such, the directory is a two-way directory. Unless otherwise indicated, or the context indicates otherwise, the terms “directory of contacts,” “contacts directory,” and “directory” may be used interchangeably in this disclosure.

The present disclosure also presents processes and apparatuses for event-based directory management. For example, processes and apparatuses disclosed herein can be used to add one or more tags to a directory of contacts. When a tag is active for a directory of contacts, and when a contact is added, the contact can be automatically added to the directory of contacts without user intervention.

As used herein, the term “user” includes individuals and entities using the application, for example, at least based on the existence of an account profile belonging thereto. As used in the singular form, “user” may refer to a human user by example. As used in the plural form, “users” may refer to one or more potential contacts and/or registered contacts. Notwithstanding the foregoing, it will be apparent that “user” may include various other embodiments as may hereinafter be described or referenced. “User” can also include an application, a script, an agent, or the like operating on behalf of, triggered by, or the like, a human user.

FIG. 1 is a diagram of an example of an apparatus 100 used with event-based directory management in accordance with implementations of the present disclosure. The apparatus 100 can also be used for detecting contact proximity and sharing contact information in accordance with implementations of the present disclosure.

The apparatus 100 may include a processor 110, a memory unit 120, a location component 130, a communication component 140, a user interface unit 150, or a combination thereof. The apparatus 100 may be an electronic device, which may be, without limitation, a smartphone, personal digital assistant, tablet computer, laptop computer, desktop computer or other Internet-connectable device.

The processor 110 may be one or more various computer processors used to process data and perform computing tasks including without limitation a central processing unit (CPU) 112, and/or a graphical processing unit (GPU) 114 as shown in FIG. 1. In some embodiments, the CPU 112 or GPU 114 may be implemented as a microcontroller, microprocessor, or an application specific integrated circuit (ASIC), or a combination thereof.

The memory unit 120 may be one or more various volatile and nonvolatile memory types including without limitation random access memory, read only memory, flash memory or other removable/non-removable storage media. The memory unit 120 may include a system memory module that may store executable computer instructions that, when executed by the processor 110, perform various user device functionalities including those described herein. The memory unit 120 may store data, including user account information or contact information, entered by the user via the user interface unit 150 or received from the communication component 140.

The location component 130 may include, for example, a global positioning system module or geolocation module, which, based on its configuration, may be in communication with satellite or other external systems used for tracking the location of an electronic device. In some embodiments, the positioning data received by the location component 130 may be one or more of a set of coordinates and a common address (e.g., a street address along with corresponding city, state/province/country information). The location component 130 may identify a location of the apparatus 100 using positioning data. The communication component 140 may send and receive electronic data including, for example, user data. The user interface unit 150 may maintain the user's account profile and user data and the user data of other users, as well as receiving user commands to be processed.

The communication component 140 may include, for example, a modem or other hardware module or adapter for connecting the electronic device to a network, such as an intranet, local network, or the Internet, either through a physical connection (e.g., Ethernet) or wireless connection (e.g., Wi-Fi). In some embodiments, the communication component may connect the user device to, and thereafter communicate with, a server and/or one or more other user devices.

The user interface unit 150 may include one or more units that may register or receive input from a user or present outputs to the user, such as a display, touch interface, a proximity sensitive interface, a light receiving/emitting unit, sound receiving/emitting unit, a wired/wireless unit, or other units. In some embodiments, the user interface unit 150 may include a display, one or more tactile elements (e.g., buttons or virtual touch screen buttons), lights (e.g., LED), speakers, or other user interface elements. The user interface unit 150 may receive user input and provide information to a user related to operation of the apparatus 100. The user interface unit 150 may include, for example, part of a software application installed on and executed by the processor 110 and configured to receive and store user data, contact data and other information stored in the memory unit 120.

In some embodiments, the user interface unit 150 may include a display screen, such as a touch screen, for displaying content and receiving user commands to be processed. The user interface unit 150 may be supported by one or more input configurations including without limitation a keyboard and/or mouse configuration, a touchscreen configuration, and a microphone and speaker configuration. In some embodiments, the user interface unit 150 may include user-selected customization features for creating and maintaining user data in an account profile. For example, the user interface unit 150 may include graphical features to enable the user to establish settings data, which may include various settings for modifying or limiting certain aspects of the software application.

The user data, the contact data, the settings data, or a combination thereof, may be stored within the memory unit 120 of the apparatus 100, within non-transient memory contained within the server, or a combination of both. For example, data associated with the user account profile may be input using the user interface unit 150, which may be immediately stored in memory unit 120 of the apparatus 100, and may be transmitted via the communication component 140 to a network server for storage in the network database within the server memory. The user data, contact data, and settings data may be communicated to the server periodically or in response to data changes, for example, to update contact data registered with various users or record select user preferences.

The account profile of the user may include user data of the user, which is viewable at least in part by certain other users. For example, “registered contacts” referred herein as network users with whom user data is being shared with the user, may view user data of the user. In some embodiments, the account profile may comprise various graphical features. For example, a picture (which may include without limitation a photograph, a computer generated image, a solid color, or a patterned image) may be uploaded to use as the background for the user account profile, or a picture may be retrieved from a library provided by the application or server. In some embodiments, the various media files, such as video, audio and picture files, may be uploaded to the account profile and made available for viewing by other users. For example, an entity user may upload commercials or other marketing materials to the account profile to promote goods and services to potential customers.

The user data may include information relative to an account profile of a user and may comprise name, title, company, availability status, account picture, phone and mobile numbers, mailing addresses, email addresses, facsimile numbers, social media links, websites, birthday, anniversary, and/or other information associated with the user. The user data may be received from a user interface. In some embodiments, user data may further include present and past location data for the user. The user data may be organized into one or more profiles (e.g., a work profile comprising the user's business contact information and a home profile comprising personal contact information), to permit the user to conveniently elect for only certain profiles to be publicly viewable, and/or to distinguish professional and personal user data for presentation to other users.

The contact data may include user data relative to registered contacts, which may be viewable by the user, for example, as a contact list accessible within the application. In some embodiments, the registration of further contact data or modification of existing contact data for a registered contact may be automatic according to user-based configuration by the user. In some embodiments, the registration of further contact data or modification of existing contact data for a registered contact may be received from a user interface in response to user entry. As an example of automatic modification, a registered contact of the user may elect to no longer share certain contact data with the user, permissions for the contact data relative to the user may be changed by the registered contact, thereby causing that contact data to no longer be viewable by the user. The contact data may be organized into one or more profiles as set by the corresponding user.

The settings data may include settings configured by the user device in accordance with selections by the user. In some embodiments, the settings data may be input to the user device via a user interface, such as the user interface unit 150 of FIG. 1. For example, an application may be executed to graphically display various configurable settings on a touch screen, and in response to user input, record and save the settings data to a memory of the user device, such as the memory unit 120. The settings data may be sent to a network server and stored in a memory unit of the network server as parameters when executing data sharing and detection of potential contacts in accordance with this disclosure. In some embodiments, the settings data may include a proximity range setting, a detection preferences setting, a user data setting, or a combination thereof.

The proximity range setting may indicate a particular proximity range relative to the user device location, within which searching and detecting of other users may be executed, such as searching and detecting potential contacts for the user within a two mile radius of the user's present location. In some embodiments, a network server may receive the proximity range setting from the user device, and may identify other users concurrently located within proximity of the user corresponding to the proximity range setting. In some embodiments, the user device may include a location detection function that uses peer-to-peer signals with a user device of another user located within a proximity of the user as defined by the proximity range setting. The proximity range setting may be fixed and unchangeable, or may be adjustable by the user.

The detection preferences setting may be defined by the user and may identify other users individually or a classification of users as potential contacts to be detected within the proximity range. For example, the detection preferences setting may be set to allow all users to be detected, or it may instead allow only certain selected users (e.g., entities that are restaurants, users identified by a first name, age, or gender, or other criteria) to be detected.

The user data setting may indicate the degree to which the user data (or specific portions thereof) is viewable by other users. In some embodiments, the user may define all or select portions of the user data as being public user data (i.e., automatically viewable by other users) or private user data (i.e., only viewable by other users upon the user granting permission therefor). The user may modify the user data setting from an initial setting. For example, the user data setting for a portion of the user data may be changed from public user data to private user data, and vice versa.

Based on the settings data, the server may detect other users located within the defined proximity range. Users who have not previously shared user data with the user, as well as users who have, but who no longer are sharing user data with the user, may be defined as “potential contacts.” Users who are currently sharing user data with the user may be defined as “registered contacts.” In some embodiments, upon detecting a potential contact, the user may send an exchange request to the potential contact by electing to share all user data, some user data, or no user data with the potential contact, provided that user data defined as public may automatically be shared upon initiating the exchange request. Upon the potential contact and the user each agreeing to share user data with one another, the user and the potential contact each become registered contacts to one another, and user data of the potential contact may be shared with the user as contact data and vice versa. In some embodiments, the user and a potential contact or registered contact may elect to enter into a private chat wherein they may communicate messages to each other.

FIG. 2 is a diagram of an example of a system 200 used with event-based directory management in accordance with implementations of the present disclosure. The system 200 can also be used for data sharing between devices based on relative proximity in accordance with implementations of the present disclosure. In some embodiments, the system 200 may include a user device 202, which may be configured as shown and described herein with reference to apparatus 100 in FIG. 1. The system 200 may also include one or more other user devices, such as the user devices 212, a network access point 222, and a network server 232. The system 200 may also include communication links 204/214/224 and network 234.

The user device 202 may communicate with the network entities via communication link 204, and may access the network server 232 via a network 234. In an example, the network 234 can be the Internet and the communication link 204 can be an internet connection. The one or more other user devices may be located within the proximity range as defined by the proximity range setting. In some embodiments, the user device 202 may communicate with the network server 232 to set up the account profile of the user and to upload the settings data onto the network server 232. The network server may detect the one or more user devices 212 as being associated with potential contacts for the user of user device 202 in response to an action by the user. For example, the user may open (e.g., start, launch, execute, etc.) an application on the user device 202, which may automatically send a signal on communication link 204 to the network access point 222 and forwarded to the network server 232 over the network 234. The signal may include the location data and/or the settings data of the user device 202. Meanwhile, one or more other users registered with the network on associated user devices 212 may have communicated respective location data to the network server on communication link 214 via the network access point 222 and the network 234. Based on the location data and/or settings data received from the user devices 202/212, the network server 232 may identify one or more user devices 212 as being located within the proximity range as set by the user device 202, and as such, are identified as potential contacts for the user of user device 202. In some embodiments, the user devices 202/212 may exchange location data directly, such as through the communication link 224, which may then be transmitted to the network server 232. In some embodiments, the communication link 224 may be a peer-to-peer communication link.

In some embodiments, the user device 202 may receive an indication from the network server 232 of user devices 212 associated with potential contacts, as identified by the network server 232. The user device 202 may display the potential contacts on a user interface, from which a potential contact may be selected for exchanging user data, such as contact information. The user device 202 may send the potential contact selection to the network server via the communication link 204. In response to the potential contact selection, the network server 232 may send a request to the user device 212 of the potential contact for exchanging contact information with the user of user device 202. If the potential contact agrees to exchange data with the user of user device 202, the data sharing may be transmitted via the network over communication links 204/214, or the data sharing may be transmitted directly via the communication link 224. In some embodiments, the user and the new contact may commence a chat session via the network over communication links 204/214, or the chat session may be transmitted directly via the communication link 224, which can be a peer-to-peer communication link. For example, a user sharing application may be activated on both the user device 202 and the user device 212 of the new contact, which enables a chat session to be initiated by either the user or the new contact.

FIG. 3 is a flowchart diagram of an example of a process 300 for data sharing between devices of FIG. 2 based on relative proximity in accordance with the implementations of the present disclosure. The process 300 may include identifying user data of a user at 302, determining a location of the user at 304, identifying a user device of a potential contact located within a defined proximity of the location of the user at 306, sending communications to initiate data sharing at 308, exchanging the data between the user the potential contact at 310, or a combination thereof.

In some embodiments, the process 300 may be implemented as a computer readable medium that stores instructions executable by processor. In some embodiments, the instructions may be stored in a memory, such as a memory in the network server 232 of FIG. 2, and may be executed by one or more processors in the network server 232. In some embodiments, the process 300 may be executed by the network server 232 to enable data sharing between user devices, such as the user device 202 and the one or more other user devices, such as the user devices 212.

In some embodiments, the user data for registered users may be identified by the network at 302. For example, the user profile of each user includes the contact information of the user, which is recorded during registration and stored by the network server 232. Any updates to the contact information may be based on user input at the user device, and may be recorded and stored by the network server 232.

In some embodiments, the location of the user device 202 may be determined at 304. As detection of potential contacts is dependent upon location data of the user, the network server 232 regularly identifies the location of the user device 202 based on location data determined by the location component and transmitted by the communication component of the user device, such as location component 130 and communication component 140 of FIG. 1. In some embodiments, the communication of location data to the server may be dependent upon the location component 130 being enabled (e.g., wherein the electronic device is a smartphone, the GPS feature must be enabled in order for the user's location data to be communicated).

In some embodiments, a potential contact located within the selected proximity range may be identified at 306. The network server 232 may maintain records of location data for all user devices in communication with the network server 232. The location of other user devices 212 may be computed, for example, by calculating the distance between the user device 202 and other user devices 212. In the event that other user devices, such as one or more of the user devices 212, are determined to be within the proximity range defined by the settings data, and subject to any detection preferences defined by the user, such other user devices as the one or more of the user devices 212 may be detected by the network server 232 based on the location data. In some embodiments, the network server 232 may notify the user that potential contacts are nearby. For example, the user device 202 may receive the notification of potential contacts, and execute a visual display for identifying the locations of potential contacts, such as by visually denoting the locations on a map. The user may then select one or more detected users to share user data with, subject to each user's user data settings.

In some embodiments, the network server may generate and send messages between the user and the potential contact related to data sharing at 308. For example, in response to the user's selection of a potential contact, a request message may be sent from the user device 202 indicating a request for an invitation message to be sent to the potential contact. The request message may include a permission setting indicating which user data and/or which user data profile of the user is selected to be shared with the potential contact. Responsive to receiving the request message, the network server 232 may generate and deliver the invitation message to the user device 212 of the potential contact. A response message may be sent from the user device 212 of the potential contact indicating acceptance or denial of the invitation. Responsive to receiving the response message, the network server 232 may generate and deliver a response message to the user device 202.

In some embodiments, the user device 202 may send the exchange request (e.g., via an electronic message) to the potential contact, via the network server 232, which the potential contact may accept, for example, by similarly selecting to share user data or entering into a chat conversation with the user. The potential contact may decline the exchange request, for example, by refusing to share any user data or refusing to enter into the chat conversation.

In some embodiments, the user device 202 may exchange data with the user device 212 of the selected potential contact at 310. The user and potential contact may each select which user data is to be shared. For example, the data exchange may be limited based on permission settings elected by the user and/or the potential contact. In response to the network server 232 receiving a message from a user device, such as the user device 202 or one of the user devices 212, of the potential contact identifying the potential contact's user data selected to be shared with the user, such as according to a permission setting, the network server 232 may send an acceptance response message to the user device 202. The network server 232 may designate the user and the potential contact as registered contacts to each other, and the user data selected to be shared by the user and the potential contact may be registered as contact data respectively. The network server 232 may execute the data sharing by sending user data of the user, such as contact information, to the user device 212 of the registered contact, and by sending user data of the potential contact, such as contact information, to the user device 202.

FIG. 4 is a diagram of an example of a user interface display for detecting contacts responsive to user input in accordance with implementations of this disclosure. In some embodiments, the user device 202 may display an application interface display 402 for initiating a detection of contacts, and after an elapsed time duration of the detection, an application interface display 412 for indicating the results of the detection of contacts may be displayed. For example, the application interface display 402 may include a detection start icon 404 to enable the user to commence a request for detection of potential contacts in the vicinity of the user device, and a detection icon 406 that may provide an indication of status for the detection being processed by the network server. For example, the user device may respond to the user touch and/or holding the touch of the detection start icon 404 by sending location information of the user device to the network server. In some embodiments, the location component 130 of FIG. 1 may remain active for as long as the activation feature is manually toggled by the user touch of detection start icon 404. In some embodiments, the detection start icon 404 may respond only to a unique identifier, such as the user's fingerprint. The application interface display 402 may provide visual feedback that may include, for example, a color change or blinking of detection icon 406 to indicate status of the detection, which may include that the detection is in progress. The application interface display 412 may include a detection icon 416 for detection status indication, such as indicating that the detection processing is completed by changing the appearance of the detection icon 416 from detection icon 406 and/or a change in appearance of detection start icon 414 compared to detection start icon 404. Contact display region 418 may indicate the results of the detection process by identifying user identification or tags of potential contacts found to be within the proximity range defined in the proximity range setting.

FIG. 5 is a diagram of an example of a user interface display for detecting contacts automatically in accordance with implementations of this disclosure. In some embodiments, the user device 202 may display an application interface display 502 for an automatic detection mode, an application interface display 512 for indicating a status change for detection of potential contacts, and an application interface display 522 that indicates that automatic detection mode has been toggled off. For example, the application interface display 502 may include a detection icon 506 that may indicate an automatic detection mode for detecting potential contacts in the vicinity of the user device, such as by a visual indication that may include an icon color. The application interface display 512 may include a detection icon 516 that may indicate a new potential contact has been automatically detected, such as by a visual indication that may include a numeral corresponding to a number of new potential contacts detected. The application interface display 522 may include a detection mode icon 528 that enables a user to toggle between automatic detection mode and user initiated detection mode, and a detection icon 526 that may indicate the status change for the automatic detection mode, such as by a change in icon color.

In some embodiments, the user activated contact detection of FIG. 4 may enable a single one-time detection search by the network server, which may conserve resources of the user device and the network. In some embodiments, automatic contact detection of FIG. 5 may enable contact detection continuously while the automatic mode is activated. For example, automatic contact detection mode may be activated by toggling one or more activation features, that may include activating the location component 130 of FIG. 1 for an unspecified period of time (e.g., until the user subsequently deactivates the location component 130), and activating the location component 130 for a specified period of time (e.g., one hour). For example, tapping the detection icon 506 once may trigger contact detection activation for an unspecified period of time, tapping the detection icon 506 twice may trigger contact detection activation for a specified period of time, and tapping the detection icon 506 three times may deactivate the location component 130 and the contact detection process. The activation features for contact detection described herein are provided as examples, and other ways of user activation and automatic activation are possible for implementations of this disclosure.

FIG. 6 is a diagram of an example of a user interface display for selecting user data for data sharing in accordance with implementations of this disclosure. In some embodiments, application interface displays 602/612/622 may display information related to data sharing between the user and a potential contact identified by the contact detection of FIGS. 4 and 5. For example, the application interface display 602 may show registered contact identifications 604 and potential contact identifications 606 that may be distinguishable by having a different visual appearance or graphical representation. In some embodiments, the registered contact identifications 604 and potential contact identifications 606 may be displayed in a list format, as shown, in response to a user input at format icon 603 selecting a list format, such as by a touch screen tapping. The registered contact identifications 604 and potential contact identifications 606 may be arranged in the application interface display 602 in various ways, including alphabetically, by proximity to the user, time of detection, or based on frequency of previous exchanges. A data exchange with a potential contact may be initiated by the user device 202 in response to receiving user input, such as by tapping the potential contact identification 606 associated with the potential contact. The user device 202 may send a request signal to the network server 232 identifying the selected potential contact and indicating the user's request for sending an invitation for data exchange from the user device 202 to the device 212 of the potential contact.

In some embodiments, the application interface display 612 may be displayed in response to the request to exchange data, and may include selectable user data of the user, from which the user may select which user data of one or more user profiles to share with the potential contact. For example, the application interface display 612 may provide options for the user to share all data via icon 613, selectively share only certain user data (e.g., only certain profiles or portions thereof), or share no user data and instead request to enter into a chat conversation with the potential contact, by selection of chat only icon 614 for example.

In some embodiments, location region 616 of the application interface display 612 may indicate a location for the user device when the user device associated with potential contact identification 606 was detected by the network and identified to the user device 202.

In some embodiments, the application interface display 622 may indicate the user selection for user data for the data exchange. For example, a share all icon 624 may be responsive to user input, such as by touch screen tapping the icon 624, and all user data of the display may be visually altered for feedback display, such as shown by a highlighted region 626, to indicate confirmation by the user device 202 for the user selection. In some embodiments, the application interface display 622 may provide an interface for the user to accept the selected data sharing information, such as by touch screen tapping the accept icon 628. In response to the user input at the accept icon 628, the user device 202 may execute a data sharing request to the network server 232.

In some embodiments, the user device 202 may provide global user data changes by the user. For example, an application interface display may be presented to the user on the user interface unit 150 which shows the user data for all user profiles of the user as recorded on the network server 232. The user data profiles may be edited at any time by the user, allowing all registered contacts to have access to current user data once the user data is edited by the user and saved to the network server 232. Unlike with one-off transmissions of contact information, or exchanging of business cards, the user need not redistribute updated contact information since the update may be global via the central repository in the network server 232.

FIG. 7 is a diagram of an example of a user interface display for identifying a potential contact based on location in accordance with implementations of this disclosure. In some embodiments, an application interface display 702 may display location information related to potential contacts, such as on a map, in response to user input at format icon 703, which may provide a selectable display for potential contacts in a map format or list format. For example, in response to user input selecting map format at format icon 703, such as by a touch screen tapping, the application interface display 702 may show markers 704 representing potential contacts in respective map locations. In some embodiments, a user input selection of a marker 704 may trigger a generation of an application interface display 712 which may show an identifier region 714 for the potential contact associated with the selected marker 704. In response to a user input, such as by touch screen tapping at the identifier region 714, an application interface display 722 may be generated for presenting selectable user data for sharing with the selected potential contact. The user may interface with the application interface display 722 as shown and described herein with respect to FIG. 6.

FIG. 8 is a diagram of an example of a user interface display for identifying a potential contact by scan code in accordance with implementations of this disclosure. In some embodiments, an application interface display 802 may display a contacts screen, including a scan icon 804 for permitting interfacing with another user device. For example, in response to a user input at the scan icon 804, such as by a touch screen tapping, an application interface display 812 may be generated and a camera in user device 202 may be activated for capturing a scan code display of a user device associated with a potential contact. In some embodiments, in response to the camera of the user device 202 being aimed at a scan code, the application interface display may show the scan code 814 as captured by the camera, and may provide markers 818 as a view finder to assist the user in centering the scan code for the camera to focus. The camera icon 816 may be responsive to a user input, such as by a touch screen tapping or sliding, and may execute the scan of the scan code. An application interface display 822 may be generated in response to the scan execution, which displays the selectable user data screen from which the user may input whether to share all user data, share some user data, or chat only, in a manner as shown and described herein with respect to FIG. 6.

FIG. 9 is a diagram of an example of a user interface display for sharing user data by scan code in accordance with implementations of this disclosure. In some embodiments, an application interface display 902 may display a scan code 904 so that another user device may read the scan code for identification as a potential contact. For example, the user device associated with scan code 904 of the application interface display 902 may be presented to another user device that operates the scan code reader, such as the user device 202 that displays captured scan code 814 in FIG. 8, where the captured scan code 814 corresponds to the scan code 904 displayed on the application interface display 902. In some embodiments, in response to receiving a request for user data sharing from another user device, such as the user device of FIG. 8, the application interface display 902 may display an indication of the received request at pending exchange icon 906, which may be responsive to user input. For example, in response to a user input at pending exchange icon 906, such as by a touch screen tapping, an application interface display 912 may be generated to display the potential contact identifier 914, which may be responsive to user input for accepting the request. In some embodiments, an application interface display 922 may be generated in response to the user input at the potential contact identifier 914, to provide selectable user data for exchange to the requester. For example, the user may input at the application interface display 922 whether to share all user data, share some user data, or chat only, in a manner as shown and described herein with respect to FIG. 6.

FIG. 10 is a diagram of an example of a user interface display for selecting location data for data sharing in accordance with implementations of this disclosure. In some embodiments, an application interface display 1002 may display information related to the data sharing with a new contact and selectable by the user for constructing the contact profile information. For example, the application interface display 1002 may indicate the location information 1004 of the user device when the potential contact was detected and may associate the location information 1004 with the new contact registration as additional contact data. The application interface display 1002 may be responsive to user input, such as by tapping the location information 1004, and may generate an application interface display 1012 that shows a representation of the location information 1004 as a map location 1014. In some embodiments, the user interface unit 150 may be responsive to the user input for adding notes or comments within the new contact registration information as further contact data.

FIG. 11 is a diagram of an example of a user interface display for user data of listed registered contacts in accordance with implementations of this disclosure. In some embodiments, an application interface display 1102 may identify registered contacts as a list in a display region 1104 responsive to user input, such as by tapping on a registered contact identification. For example, in response to tapping on registered contact identification in display region 1104, an associated application interface display 1112/1114/1116 may be generated and displayed on a user interface display, such as the user interface unit 150 of FIG. 1. The application interface display 1112/1114/1116 may show contact data for a given registered contact to be viewed by the user as a contact profile, which may include aspects of the registered contact's account profile, such as the customizable features of profile background pictures and associated media. The viewable contact data for a given registered contact correlates to the permissions set by the registered contact, such as any public user data and/or the private user data that the registered contact has agreed to share.

FIG. 12 is a diagram of an example of a user interface display for changing data sharing in accordance with implementations of this disclosure. As described herein, and notwithstanding the permissions originally set during an exchange of user data, in some embodiments, the user interface unit 150 may display configurable permission information set for various user data shared with a given registered contact. For example, the permission information may be displayed and may be responsive to user input for electing to share more or share less user data with registered contacts. In some embodiments, an application interface display 1202 may indicate a registered contact in display region 1204, which may be responsive to user input, such as by tapping the display region 1204. In response to the user input, an application interface display 1212 may be generated and displayed to include an editing icon 1214, which may be responsive to a user input. For example, an application interface display 1222 may be generated and displayed to show shared contact information 1224 previously defined for sharing with the registered contact. The shared contact information may be modified in response to user input on the application interface display 1222. For example, the user may select certain shared user data and remove it from the contact data registered with the registered contact, without altering the user account profile information, which may remain intact as user data for future data sharing. In some embodiments, the application interface display 1222 may modify shared user data by deleting an entire contact profile and removing all contact data relating to the registered contact in response to user input. In response to the modification to the contact profile by the user device of the user, the network server 232 may modify the user's contact registration to reflect the deletion, and in turn, may delete all contact data of the user within the registered contact's records.

FIG. 13 is a diagram of an example of a user interface display for following registered users in accordance with implementations of this disclosure. In some implementations, an application interface display 1302 may respond to user input for following one or more registered users. For example, a registered user identification appearing in display region 1304 may be responsive to user input, such as by tapping the identification on the display, for selection as an entity to be followed by the user. An application interface display 1312 may be generated and displayed in response to the user input, and may include follow icon 1314. In response to user input, such as by tapping the follow icon 1314, an application interface display 1322 may be generated and displayed with a prompt for the user to confirm that the user has selected to follow the entity. On a condition that the user confirms the selection, the application interface display 1332 may be generated and displayed for indicating that the user device will follow the selected entity. A following icon 1334 indicates that the user is now following the selected entity. As a result of the user device following the selected entity, the network server 232 may send the entity's posts on the network to the user device, and the posts may be displayed on the user interface as a dedicated content feed viewable by the user.

FIG. 14 is a diagram of an example of a user interface display for following registered contacts in accordance with implementations of this disclosure. In some embodiments, an application interface display 1402 may show a list of followed contacts in display region 1404, which upon selection by the user, such as by tapping the followed contact identification, an application interface display 1412 may be generated and displayed to show the followed contact's content feed information. In some embodiments, the application interface display 1412 may provide options for the user to view information associated with the followed contact, which may include icons 1414/1416/1418/1420 responsive to user input. For example, the user may view the content feed associated with the followed contact by selecting the media icon 1414, or view media associated with the followed contact by selecting the media icon 1416, record notes or comments about the followed contact within the contact profile by selecting the clipboard icon 1418, or recommend the followed contact to other users by selecting the envelope icon 1420. In some embodiments, only contacts whose user data is set to public may be recommended to other users.

FIG. 15 is a diagram of an example 1500 of a user interface display for creating a directory of contacts. The example 1500 illustrates a user home page 1502. The user home page 1502 can be displayed on a user device in accordance with implementations of this disclosure. The user device can be the apparatus 100 of FIG. 1. The user home page 1502 can include an area where directories of contacts created by, or available to, the user are displayed. For example, a section 1504, labeled “Directory,” can display the directories created by the user. The section 1504 illustrates that directory 1508 (labeled “Starbucks”) is a directory created by the user. The user home page 1502 can include a user interface control that, when invoked, allows the user to create a new directory of contacts. For example, the section 1504 can include the control 1506 (labeled “+New”), which, when invoked (i.e., activated) by the user, permits the user to create a new directory of contacts. The user who creates a directory of contacts is referred to herein as the “administrator” of the directory of contacts.

The example 1500 illustrates a create user interface 1510 that can be presented to the user in response to the user activating the control 1506. The create user interface 1510 can include a data entry field 1512. The user can provide, via the data entry field 1512, a name for the directory of contacts to be created. A create user interface 1511 illustrates that the user has provided a directory name of “Starbuck” in a name field 1514. In response to the user activating the OK control 1518, a request to create the directory of contacts may be transmitted, from the user device to a server, such as the network server 232 of FIG. 2.

In some implementations, a uniqueness check can be performed by the server to determine whether the directory name provided by the user is unique (i.e., not a duplicate name). In the case where the uniqueness check does not pass (i.e., the name is already used as the name of another directory), then the directory of contacts is not created. For example, since the user already has a directory of contacts named “Starbucks” (i.e., the directory 1508), an error message, such as an error message 1516, can be received from the server indicating that the directory name (i.e., “Starbucks”) is already taken and that the user is requested to enter another name.

In some implementations, uniqueness is checked based on the list of directories of the user. For example, if a first user already has a directory named “Ginko,” and a second user, who does not have a directory named “Ginko,” attempts to create a directory named “Ginko,” the request to create the directory “Ginko” succeeds (i.e., the directory is created) because the second user does not have a directory named “Ginko.”

In other implementations, directory names are globally unique. That is, the directory names are unique across all users. For example, and referring back to the “Ginko” example, the request from the second user to create a directory named “Ginko” fails because a directory named “Ginko” (i.e., the first user's directory) already exists. In still other implementations, directory name uniqueness is determined based on a subset of users. For example, if the second user's email address is “user2@somecompany.com,” uniqueness can be checked based on the directory names of all users in the “somecompany.com” domain. Other ways of determining the subset of the users are available. In still other implementations, uniqueness is not checked and multiple directories having the same name are possible. The uniqueness scope (e.g., user, global, none, domain-based, etc.) can be a server configuration, such as a configuration of the network server 232 of FIG. 2.

In the case where the uniqueness check passes or no uniqueness check is performed, then the user can be presented with another interface (e.g., a settings interface 1520) to provide additional settings for the directory of contacts. The additional settings for the directory can include a permissions setting and directory joining criteria. Permissions can indicate whether a directory is public or private (as further described below). Directory joining criteria can be used to determine whether a user, attempting to join the directory, should be added to the directory (as further described below).

The settings interface 1520 can include a permissions controls 1522 and other controls which can be used by the administrator for providing directory joining criteria. For example, the settings interface 1520 includes a domain setting 1524 for providing directory joining criteria. The settings interface 1520 is further described below with respect to FIGS. 16-17.

FIG. 16 is a diagram of an example 1600 of a user interface display for setting permissions for a directory of contacts in accordance with implementations of this disclosure. The example 1600 includes the permissions controls 1602, which can be used for setting permissions for a directory of contacts.

The example 1600 illustrates setting permissions via radio buttons. However, other user interface controls are possible. To set the directory to be “private,” a control 1608 can be selected. To set the directory to be “public,” a control 1610 can be selected. When the control 1608 is selected, controls 1612 and 1614 can become available. That is, when the control 1610 is selected, the controls 1612 and 1614 can be deactivated (i.e., they become unavailable for user selection), hidden, or the like. When the control 1608 is selected, the controls 1612 and 1614 can become active and/or visible. Selecting the combination of the control 1608 and the control 1612 (i.e., as illustrated in the settings of the permissions controls 1602) sets the directory permission to “private-auto.” Selecting the combination of control 1608 and the control 1614 (i.e., as illustrated in interface 1604) sets the directory permission to “private-manual.” Selecting the control 1610 (i.e., as illustrated in an interface 1606) sets the directory permission to “public.” Other permissions are also possible. The labels “private-auto,” “private-manual,” and “public” are merely labels used as short-hand to refer to the semantics associated with each of the labels. Other labels and/or techniques for implementing the semantics associated with these labels can be used.

The semantics of “private-auto,” “private-manual,” and “public” are now described. A “public” directory can be discoverable (by any means) by any user. For example, a user can discover a directory of contacts by listing the names of all the available directories (i.e., available on a system, such as the network server 232). For example, a user can discover a directory by searching using partial directory names, wild cards, by administrator name, by other criteria, or any combination thereof. A user can discover a directory by receiving a pointer (e.g., a hyperlink, a contact card, etc.) to the directory. The user can discover the directory by other means. Any user can join a “public” directory. By “joining” a directory, the user (i.e., the user's contact information) becomes available in the directory of contacts.

In an example, a “private” directory is not discoverable. In such a case, the user can join the directory of contacts only by receiving an invitation to join the directory. In an example, the invitation must be received from the administrator of the directory. In another example, the invitation can also be received from other members of the directory.

In another implementation, a “private” directory can be discovered. However, when a user requests to join the directory, additional checks may be performed before the user can be joined (i.e., added to the directory). If the directory is “private-manual,” the user's request to join the directory is forwarded to the administrator. If the administrator approves the request, then the requesting user is added to the directory.

If the directory is “private-auto,” then the directory joining criteria can be checked against the requesting user's contact information to determine whether the user is to be added to the directory. In an example, all criteria must be satisfied for the user to be added. In another example, at least some of the criteria must be satisfied. In another example, each criterion can have a weight and the weighted sum of matched criteria must exceed a threshold value for the user to be added. Other directory joining criteria matching options are possible.

FIG. 17 is a diagram of an example 1700 of a user interface display for setting directory joining criteria in accordance with implementations of this disclosure. The example 1700 includes the settings interface 1520 of FIG. 15, which includes the domain setting 1524. The domain setting 1524 includes a control 1702, which, when activated, causes interface 1704 to be displayed. The interface 1704 can be used by the administrator to provide one or more domain names as directory joining criteria. For example, the domains 1706 illustrate that two domains (i.e., “hotmail.com” and “msn.com”) were provided via the interface 1704. The domains 1706 can be displayed in the order they were provided by the user or alphabetically. Other ordering and/or sorting of the domains 1706 are possible.

In the example 1520 of directory joining criteria, before a user is added to the directory, the user's contact information can be checked to determine whether the user contact information matches (partially, fully, or otherwise) the directory joining criteria. For example, assume that a user with an email address of “bob@acme.com” requests to join a private-auto directory. Since the user's domain (i.e., “acme.com”) does not match any of the domains “hotmail.com” and “msn.com,” then the user is not automatically added to the directory. In one example, the user's request is rejected and the user is not added to the directory of contacts. In another example, the system can send a notification, to the user, of the directory joining criteria. For example, the notification can state “To join this directory, your profile must include a @hotmail.com or a @msn.com email address. Please update your profile and try to join again.” The notification can be sent via any means. For example, a push notification, an email notification, an application notification, or the like can be used to send the notification to the user. The user can be added to the directory once the user's contact information is updated to match the directory joining criteria. For example, when the requesting user adds a secondary email address (e.g., bob@msn.com) that matches the directory joining criteria, the user can be added to the directory.

Other directory joining criteria are possible. For example, the joining criteria can indicate users to be excluded from the directory. For example a black (i.e., excluded) list of domains (i.e., excluded domain names) can be provided. For example, if the directory is that of an enterprise (e.g., a company), the black list can list the domains of the enterprise's competitors. As such, an employee of a competitor may not be automatically added to the directory. All other users can be automatically added. The directory joining criteria can indicate geographic criteria. As such, the directory joining criteria can include a location-based criterion. For example, the administrator can indicate that only users in the state of Michigan can be automatically added. For example, the administrator can indicate that only users within a 25 mile-radius of the administrator's location can be automatically added. The administrator's location can be based on the user's address, as may be specified in the administrator's profile. The administrator's location may be dynamic. That is, the administrator's location can be based on the location of the administrator's user device at the time that a user request to join the directory is received. The system can use the requesting user's contact information (e.g., address or device location) to determine whether the requesting user matches the criteria.

FIG. 18 is a diagram of an example 1800 of a user interface display for editing a directory of contacts in accordance with implementations of this disclosure. The example 1800 includes the user home page 1502 of FIG. 15. The example 1800 includes a user interface 1802 for displaying the settings of a directory. For example, in response to an administrator's action (e.g., tapping, double clicking via a pointer, or the like on the directory 1508), the user interface 1802 can be displayed. The user interface 1802 can include a control 1804, which, when activated, causes the directory displayed in the user interface 1802 to be removed. That is, when the control 1804 (labeled “Remove Directory”) is activated (e.g., clicked), the Starbucks directory is removed by the system. When a directory is removed, the system can remove the directory from each of the directory's members' list of directories. For example, listing 2002 of FIG. 20 displays a listing of directories for a user. If the directory “Donghia Furniture” (i.e., entry 2006) is removed by the administrator of the directory, then the directory “Donghia Furniture” is removed from the listing 2002.

The user interface 1802 can include an edit control 1806. When invoked, the edit control 1806 causes an edit user interface 1808 to be displayed. The edit user interface 1808 allows the user to modify the name and settings of the directory. The name and settings of the directory are as described with respect to FIGS. 15-17. If the user attempts to modify the name of the directory by providing a new name in the field 1810, the system can perform a uniqueness check as described above. If the uniqueness check fails, an error 1818 can be displayed to indicate to the user that the provided name is not available for use.

The edit user interface 1808 can include a control 1812, which, when invoked for a domain, removes the domain from the directory joining criteria. In one example, when a domain is removed, members of the directory having the removed domain can be removed from the directory and the directory is removed from the removed members' list of directories. In another example, members are not removed from the directory. In either case, the altered joining criteria can apply to new requests to join the directory of contacts. The edit user interface 1808 can include an indicator 1814, which is displayed in the case of unsaved changes. The edit user interface 1808 can also include a control 1816, which, when invoked, can display a requests interface 1902 as described with respect to FIG. 19.

FIG. 19 is a diagram of an example 1900 of a user interface display for listing requests associated with a directory of contacts in accordance with implementations of this disclosure. The example 1900 includes the requests interface 1902. The requests interface 1902 includes a content area 1912 and controls 1904-1910. The content area 1912 can display different information, depending on which of the controls 1904-1910 is selected.

The control 1904 causes an invite contacts list to be displayed in the content area 1912. The invite contacts list displays a list of the administrator's contacts (i.e., users). The administrator can select one or more of the users listed in the content area 1912 and send requests to the selected user(s) to join the directory. The requests can be sent via the server. That is, a request initiated by the administrator is received and processed by the server. Unless otherwise indicated, a request sent from, or initiated by, an administrator and/or an invitee, such as via a user interface, can be received and processed by the server, such as the network server 232 of FIG. 2. The server can then forward the request to the one or more users. A request can include any action initiated through a user interface where such action affects any aspect of a directory of contacts.

The control 1906 causes a pending list to be displayed in the content area 1912. The pending list displays the list of contacts (i.e., users) to whom the administrator sent a request (i.e., an invite) to join the directory, such as described with respect to the control 1904, but who have not yet accepted the invitation. The requests interface 1902 can include user interface controls that the administrator can use to revoke an invitation. For example, by deleting a user from the pending list, the user's invitation to join the directory can be revoked. A request to revoke the invitation can be received at, and processed by, the server, which revoke the invitation. When an invitee's request is revoked, the invitee cannot accept the invitation to join the directory. In an example, a revoked request can be removed from the invitee's pending requests (described below with respect to FIG. 24). In another example, the revoked request is not removed. However, upon attempting to accept the invitation, the invitee can be notified that the invitation is revoked.

When an invitee (i.e., a user that received a request, or invitation, from an administrator to join a directory) accepts the request, the user becomes a confirmed user. A confirmed user can access the directory. By accessing the directory, the user can have access to the contact information of other users in the directory and can communicate with those other users. The control 1908 causes a confirmed list to be displayed in the content area 1912. The confirmed list is the list of invitees who have accepted the administrator's request to join the directory. The directory administrator can remove users from the confirmed list. A request to remove a user from the confirmed list can be received from the administrator at, and processed by, the server to remove the user from the confirmed list. When a user is removed from the confirmed list, the user can no longer access the directory and the directory can be deleted from user's list of directories. The confirmed list can include the members of a private directory. In an example, the confirmed list can include the members of a public directory. In another example, the confirmed list does not display the members of a public directory.

The control 1910 causes an incoming requests list (i.e., list of incoming requests) to be displayed in the content area 1912. The incoming requests list includes the users who requested access to the administrator's directory. For example, the incoming requests list can be displayed for a private-manual directory. For a private-auto directory, the incoming requests list can include the users who could not be automatically added to the directory because, for example, the users did not satisfy the directory joining criteria. The administrator can accept or reject an incoming request. For example, the user can select one (or more) incoming request(s), and via one control (e.g., a check mark control) accept the selected request(s), and via another control (e.g., a trash can control) reject the request(s). When the administrator accepts a request (i.e., authorizes the access to the directory), the user associated with the accepted request can be added to the confirmed list.

FIG. 20 is a diagram of an example 2000 of a user interface display for joining a directory of contacts in accordance with implementations of this disclosure. The example 2000 includes the listing 2002. As described above, the listing 2002 can include entries for directories that the user has joined (i.e., is a member of). For example, the entry 2006 indicates that the user is a member of the directory named “Donghia Furniture,” which is created by the administrator “Ginko.” The listing 2002 can include other entries in addition to directories of contacts. Items listed in the listing 2002 can include adornments. The adornments can provide additional information regarding an entry in the listing 2002. For example an adornment 2007 can indicate, via a color indicator, the type of the entry. For example, a green color can indicate that the entry 2006 is of type directory of contacts. The adornment can indicate the number of members of the directory. For example, the adornment 2007 indicates that the directory named “Donghia Furniture” includes one user (i.e., one contact information).

Means for joining a directory can be available to the user. For example, to join a directory, the user can activate the control 2004, which, when activated, causes the interface 2008 to be displayed. Via the interface 2008, the user can provide the name, or the partial name, of a directory to join. For example, the user can type in a field 2010 the name of the directory. Other ways can be available for the user to provide a directory name. For example, the user can search for a directory by providing search criteria. For example, the user can scroll and select from a list of all discoverable directories. If the directory provided is not available (e.g., no matching directory found, the directory is not active, the directory is deleted, etc.), then an error message 2011 can be displayed to the user. The error message 2011 can instruct the user that the provided directory could not be found and that the user is to provide another directory name.

If a directory matching the provided name is available, then a permissions interface 2012 similar to the application interface display 822 of FIG. 8 can be presented to the user. Via the permissions interface 2012, the user can indicate whether to share all user data, share some user data, or chat only, in a manner as shown and described herein with respect to FIG. 6, with other members of the directory. A feedback message can be provided to the user after the user provides the sharing information via the permissions interface 2012.

FIG. 21 is a diagram of an example 2100 of feedback messages when successfully joining a directory of contacts in accordance with implementations of this disclosure. If the directory is a public directory, a message similar to feedback message 2102 can be provided to the user. The feedback message 2102 can indicate that the user has successfully joined the directory and that a directory icon will appear in the listing 2002 of FIG. 20. When a user joins a directory, the user's contact can be added to the administrator's confirmed list as described above with respect to the control 1908 of FIG. 19.

If the directory is a private-manual directory, then a feedback message similar to feedback message 2104 can be provided to the user. The feedback message 2104 can indicate to the user that a notification is sent to the administrator so that the administrator can approve the user's request to join the directory. The notification can be sent, by the server and to the administrator, via any means possible, such as a push notification, email, other means, or a combination thereof. The request to join the directory can also be displayed in the administrator's pending list as described above with respect to the control 1906 of FIG. 19.

If the directory is a private-auto directory, and the directory joining criteria are matched, then a feedback message similar to feedback message 2106 can be provided to the user. The feedback message 2106 can indicate to the user that a validation link is sent to the user's email and that the access to the directory is granted when the user clicks the link. For example, in the case where the directory joining criteria include the domain “msn.com” (as described above with respect to FIG. 17), and the user's contact information includes the email address bob@msn.com, then a validation link can be sent to bob@msn.com. Receiving, such as by the server, an indication that the link is clicked validates that the user's email address bob@msn.com is a valid email address. In some examples, and depending on the directory joining criteria, a different validation technique may be available. In some examples, and depending on the directory joining criteria, no additional validation may be required. For example, if the directory joining criteria are such that “users within a 25 mile-radius of the administrator” can join the directory, no additional validation may be required from the user as the server may determine the matching of the criteria without additional validation from the user. For example, the server can use the user's device location and/or the user's address (if provided in the user's profile) to determine proximity to the administrator. In such cases, a message similar to the feedback message 2102 can be provided to the user.

In the case where the user submits multiple requests to join a private-manual directory, then a feedback message similar to feedback message 2108 can be provided. The feedback message 2108 can indicate that the user's request is pending approval by the directory administrator.

In the case where the user submits multiple requests to join a private-auto directory and the user has not been validated, such as by the user clicking a link that is sent to the user, another validation link can be sent to the user and a feedback message similar to feedback message 2110 can be provided. The feedback message 2110 can indicate to the user that the same (or another) validation link was resent to the user. The feedback message can instruct the user to confirm the link in order to gain access to the directory. The user can confirm the link by, e.g., clicking on the link.

FIG. 22 is a diagram of an example 2200 of a feedback message when domain directory joining criteria are not matched in accordance with implementations of this disclosure. For example, if the user's contact information does include an email address that matches the domain directory joining criteria (as described above with respect to FIG. 17), then a feedback message similar to feedback message 2202 can be provided to the user. The feedback message 2202 can describe to the user the directory joining criteria (e.g., that the user “must have a domain of gmail.com to join the directory”). The feedback message can instruct the user on how to remedy the deficiency so that the directory joining criteria can be matched. For example, the feedback message 2202 can indicate to the user “add and validate a matching email domain” and then “resubmit the request” to join the directory. The user can be navigated to an appropriate user interface to remedy the deficiency. For example, upon activating a button 2204 of the feedback message 2202, the user can be navigated to an interface (e.g., login settings 2208) via which the user can update the user's contact information to include an email with a gmail.com domain. If the user activates a close control (e.g., close button 2206), the request to join the directory can be canceled and the user can be returned to the listing 2002 of FIG. 20.

FIG. 23 is a diagram of an example 2300 of requesting to join a directory of contacts that is already joined in accordance with implementations of this disclosure. In the example 2300, the user requests to join a directory of which the user is already a member. For example, the administrator of the directory may have already granted the user access to the directory. In the interface 2008 (described above with respect to FIG. 20), the user requests to join a directory named “Atrient Inc.,” which the user has already joined. A feedback message, such as feedback message 2304, can indicate to the user that the user already has “access to this directory.” Upon acknowledging the feedback message (e.g., by activating a close button 2305), the user can be navigated to the directory. For example, upon activating the close button 2305, user interface 2306 can be displayed. The user interface 2306 can list the members of the directory of contacts (e.g., “Atrient Inc.”).

FIG. 24 is a diagram of an example 2400 of requests issued by and requests received by a user to join a directory of contacts in accordance with implementations of this disclosure. The listing 2402 displays the list of requests initiated by the user. That is, the listing 2402 displays the list of requests to join directories that the user of the listing 2402 initiated. For example, the request 2404 indicates that it is a request that the user sent on Jul. 18, 2016 (request date 2406) to the administrator “Ginko” (a directory administrator 2410) to join the directory named “Big John” (a directory name 2408). While a request is pending, the user can modify the permission level (for example, as described with respect to the permissions interface 2012 of FIG. 20). While a request is pending, the user can cancel the request to join the directory. If the request is canceled, then the request can be removed from the administrator's pending list as described above with respect to the control 1906 of FIG. 19. That is, for example, the server can receive a cancellation request from the user and, in response, remove the incoming request from the list of incoming requests and/or pending requests.

The listing 2412 displays the list of requests (i.e., invitations) that the user received from administrators to join respective directories of the administrators. For example, the invitation 2414 is received on Mar. 16, 2016 (invitation date 2416) from administrator “Ginko” (a directory administrator 2420) to join the directory “smile927” (a directory name 2418). The user can reject a request (for example, by deleting the request). If a request is rejected, the administrator can be notified that the user rejected the request to join the directory. The user can accept the invitation. If the user accepts the invitation, the user can provide the permission level. For example, the user can be navigated to the permissions interface 2012 as described with respect to FIG. 20. The user can modify to permission level at any time while the user is a member of the directory.

FIG. 25 is a process 2500 for creating a directory of contacts in accordance with an implementation of this disclosure. The process 2500 can be implemented, for example, as a software program that can be executed by a system, such as the network server 232 of FIG. 2. The software program can include machine-readable instructions that can be stored in a memory, such as the memory unit 120 of FIG. 1, and that can be executed by a processor, such as the processor 110 of FIG. 1, to cause the system to perform the process 2500. The process 2500 can implement teachings consistent with the descriptions of FIGS. 1-24.

At 2502, the process 2500 receives a first request to create the directory of contacts. The request can be received from a first user device, such as the user device 202 or 212 of FIG. 2. The first user device can be associated with a first user. The first user can be an administrator. The request can be consistent with a request as described with respect to FIG. 15. The request can include a permission. The permission can be a permission consistent with the permissions described with respect to FIG. 16. That is, the permission can indicate that the directory can be a private-auto, a private-manual, or a public directory of contacts.

At 2504, the process 2500 receives a second request to join the directory of contacts. The request can be received from a second user device, such as the user device 202 or 212 of FIG. 2. The second request can be a request that is consistent with a request described with respect to FIG. 20.

At 2506, on a condition that the permission includes a first indicator that the directory of contacts is private-manual, the process 2500 performs 2508 and 2510. For example, if the directory is private-manual, then the process 2500 can perform 2508 and 2510. At 2508, the process 2500 can sent a notification of the second request to the first user. For example, the process 2500 can send the notification to the administrator of the directory as described with respect to FIG. 20 and the feedback message 2104 of FIG. 21. At 2510, the process 2500 adds the second user to the directory of contacts in response to the second user accepting the first request. For example, the second user is added to the directory when the administrator of the directory of contacts accepts the request from the second user to join the directory as described with respect to the requests interface 1902 of FIG. 19.

At 2512, on a condition that the permission includes a second indicator that the directory of contacts is private-auto and the first request includes a directory joining criterion, the process 2500 proceeds to 2514. The directory joining criterion can be as described with respect to FIG. 15. At 2514, in response to determining that the second user meets the directory joining criterion, the process 2500 adds the second user to the directory of contacts. The process 2500 can determine that the second user meets the directory joining criterion as described with respect to FIGS. 17 and 22.

At 2514, on a condition that the permission comprises a third indicator that the directory of contacts is a public directory, the process 2500 adds the second user to the directory of contacts. If the directory of contacts is set up as a public directory (for example, as described with respect to the control 1610 of FIG. 16), the process 2500 can add the user to a public library consistent with the description of FIG. 20 and the feedback message 2102 of FIG. 21.

In an example, and as described with respect to FIGS. 17-18, the directory joining criterion can include a domain name. As such, determining that the second user meets the directory joining criterion includes determining that a profile of the second user comprises an email address that includes the domain name.

In an example, and as described above with respect to the black list, the directory joining criterion can include an excluded domain name. As such, determining that the second user meets the directory joining criterion can include determining that a profile of the second user does not include an email address that includes the excluded domain name.

In an example, and as described with respect to FIG. 19, in response to determining that the second user does not meet the directory joining criterion, an incoming request can be added to a list of incoming requests of the first user (i.e., the administrator of the directory of contacts). In an example, and as described above, the user can be added to the directory of contacts when the administrator accepts the incoming request. That is, in response to receiving an acceptance of the incoming request from the first user, the second user can be added to the directory of contacts. In an example, as described with respect to FIG. 24, the second user can cancel the request to join the directory. In response to receiving the cancellation request, the request to join the directory can be removed from the list of incoming requests of the first user (i.e., the administrator of the directory).

FIG. 26 is a process 2600 for joining a directory of contacts in accordance with an implementation of this disclosure. The process 2600 can be implemented, for example, as a software program that can be executed by a system, such as the network server 232 of FIG. 2. The software program can include machine-readable instructions that can be stored in a memory, such as the memory unit 120 of FIG. 1, and that can be executed by a processor, such as the processor 110 of FIG. 1, to cause the system to perform the process 2600. The process 2600 can implement teachings consistent with the descriptions of FIGS. 1-24.

At 2602, the process 2600 receives a first request to join the directory of contacts. The request can be received from a first device associated with a first user, such as the user device 202 or 212 of FIG. 2. The first user device can be associated with a first user. The first user can be an administrator. The request can be consistent with the description of the control 1904 of FIG. 19. The request can be a request sent from the administrator of a directory of contacts to an invitee. The request constitutes an invitation to the invitee to join the directory. The directory of contacts includes a permission. The permission can be a permission consistent with the permissions described with respect to FIG. 16. That is, the permission can indicate that the directory can be a private-auto, a private-manual, or a public directory of contacts.

At 2604, on a condition that the first user is an invitee and the permission indicates that the directory of contacts is a public directory, the process 2600 adds the first user to the directory of contacts.

At 2606, on a condition that the first user is an invitee and the permission indicates that the directory of contacts is a private-auto directory, the process 2600 adds the first user to the directory of contacts in response to determining that the first user meets a directory joining criterion. The directory joining criteria can be as described with respect to FIG. 15.

In an example, and as described with respect to FIG. 18, the process 2600 can include receiving, from the administrator of the directory of contacts, a modification of the permission. The modification of the permission can cause the first user to no longer meet the directory joining criterion. In an example, when a user no longer meets to permission, the user is removed from the directory of contacts.

In an example, an administrator of the directory of contacts can invite (such as described with respect to the control 1904 of FIG. 19) a user from the list of the administrator's contacts to join the directory of contacts. If an invitation is initiated by the administrator of the directory of contacts, the invitee can be added to the directory of contacts without checking the permissions of the directory of contacts. As such, the process 2600 can include receiving, from a second device associated with a second user, a second request to join the directory of contacts; and on condition that the second request is in response to an invitation from an administrator of the directory of contacts, adding the second user to the directory of contacts without checking the permission.

In an example, permissions are not checked in response to a system configuration and/or a directory of contacts setting to “ignore permissions” when invitations are sent by the administrator of the directory of contacts. For example, a profile of the administrator can include a setting that the administrator can toggle to “ignore permissions” or to “check permissions” for invitations sent by the administrator. In another example, a setting can be associated with a particular directory of contacts to “ignore permissions” or to “check permissions.” For example, the settings interface 1520 of FIG. 15 can include a user interface control (now shown) that allows the administrator of the directory of contacts to select either “ignore permissions” or “check permissions.”

In an example, an administrator of a directory of contacts can remove any user from the directory of contacts. When the administrator of the directory of contacts removes a user from the directory of contacts, the directory of contacts can be silently (e.g., without notification to the user) from the user's list of directory (such as the listing 2002 of FIG. 20).

In an example, an administrator of a directory of contacts can, at any time, remove himself/herself from and/or add himself/herself to any directory that the administrator creates or administers.

In a typical scenario, a user, such as a user of the user device 202, and as described above, may have multiple contacts, which the user can organize into one or more directories of contacts. For example, and as described with respect to FIG. 3, the user may exchange data with a potential contact and that potential contact can become a contact for the user. A potential contact can become a contact of the user in any other way described above.

As also mentioned above, the user can have multiple directories, as illustrated and described with respect to the listing 2002 of FIG. 20, which displays a listing of directories for the user.

FIG. 27 is an example 2700 of directories of contacts in accordance with implementations of this disclosure. The example 2700 includes a listing of directories, namely a listing 2702. The listing 2702 is similar to the listing 2002 of FIG. 20. The listing 2702 includes a directory of contacts that is named (e.g., labeled) “IO 2018 Conference,” namely a directory 2704. For example, the administrator of the directory 2704 may have intended to add to the directory 2704 all contacts that the user meets (i.e., with whom the administrator exchanges information such as described above) at the “IO 2018 Conference.”

An adornment 2706 indicates that the directory 2704 currently includes only one contact. A directory listing 2708 indicates that a contact 2710 (i.e., the contact named “RJ Czajka”) is the one member of the directory 2704. To add contacts to the directory 2704, a user interface element, such as a button 2716, may be available, which, when activated, causes a contact selection interface 2718 to be launched (e.g., opened). The contact selection interface 2718 can be used by the user to search for and/or select contacts to add to the directory listing 2708. Manually adding contacts to a directory of contacts can be cumbersome. Additionally, remembering which directory (or directories) it is desirable to add a contact to may also become cumbersome and error prone.

FIG. 28 is a process 2800 for creating a directory of contacts in accordance with an implementation of this disclosure. The process 2800 can be implemented, for example, as a software program that can be executed by a system, such as the network server 232 of FIG. 2. The software program can include machine-readable instructions that can be stored in a memory, such as the memory unit 120 of FIG. 1, and that can be executed by a processor, such as the processor 110 of FIG. 1, to cause the system to perform the process 2800. The process 2800 can implement teachings consistent with the descriptions of FIGS. 1-27.

At 2802, the process 2800 creates a directory of contacts. For example, the server, such as the network server 232 of FIG. 2, may receive a request to create the directory of contacts and may create the directory of contacts in response to the request. The request to create the directory of contacts may be received from a user device, such as the user device 202 of FIG. 2. One or more user interfaces and/or controls, such as those described above, including one or more of the interfaces and/or controls described with respect to FIGS. 15-18 may be used by the user to initiate the request, to the server, to create the directory of contacts.

At 2804, the process 2804 receives an event-based joining tag for the directory of contacts. The event-based joining tag can be used, such as by the server, to add contacts to the directory of contacts. In an example, the user of the user device may invoke (e.g., activate, press, click, or the like) a set-tag control to set an event-based tag for the directory. As such, the server can receive from the user device the event-based joining tag, as set via user interfaces of the user device.

In an example, the set-tag control can be available from a directory listing. For example, a set-tag control 2712 is shown as being available from the directory listing 2708. In such cases, a directory of contacts (e.g., the directory 2704) is already active and can be the directory of contacts for which the event-based joining tag is received. That is, the directory 2704 can be the said to be the context for the event-based joining tag; or that the server uses the directory 2704 as the context to which the event-based joining tag is assigned.

The set-tag control 2712 can include an adornment 2714 that indicates whether an event-based tag is enabled for the directory of contracts. In an example, a color can be used as an adornment to indicate whether an event-based tag is enabled for the directory of contracts. For example, a green adornment can indicate that one or more tags are active for the directory of contacts. For example, a red adornment can indicate that no tags are active for the directory of contacts. Other colors, adornments, and/or visual indicators can be available to indicate whether tags are active for a directory of contacts.

In another example, the user interface control (i.e., the set-tag control 2712) can be available additionally, or instead, in other user interfaces. For example, the set-tag control can be available from a home page, such as the user home page 1502 of FIG. 15; a directories listing, such as the listing 2002 of FIG. 20 and the listing 2702 of FIG. 27; other interface screens; or a combination thereof. In such cases, no directory of contacts is active (e.g., no context is active) for which an event-based joining tag can be set by the user. As such, activating the set-tag control can invoke another interface (not shown) that allows the user to search for and/or select one or more directories of contacts for which an event-based joining tag can be set by the user and subsequently received by the server.

FIG. 29 illustrates examples 2900 of user interfaces for setting an event-based joining tag in accordance with implementations of this disclosure. A tag setting interface 2902 can be used to set an event-based joining tag. The tag setting interface 2902 can be activated (i.e., launched, displayed, etc.) in response to activating (such as by the user) of the set-tag control 2712 of FIG. 27.

The tag setting interface 2902 includes an on-button 2904 and an off-button 2922. Only one of the on-button 2904 and the off-button 2922 can be selected (e.g., set, activated, etc.) at a time. By activating the off-button 2922, any event-based joining tags for the directory of contacts are turned off (e.g., deactivated). As such, when the off-button 2922 is activated, a message 2924 (or a similar message) can be displayed to indicate to the user that an added contact (e.g., a contact with whom contact information is exchanged, such as described with respect to FIG. 3) is not added to the directory of contacts. The message can additionally, or alternatively, indicate to the user that, to add contacts automatically to the directory of contacts, the user should enable (e.g., activate, turn on, etc.) the on-button 2904.

As a person skilled in the art appreciates, while radio buttons are used to illustrate the on-button 2904 and off-button 2922, other user interface controls can be used. Also, as a person in the arts appreciates, a selected (e.g., activated) radio button can be displayed as a filled-in circle, whereas an unselected (e.g., deactivated) radio button can be displayed as an empty circle.

When the user selects the on-button 2904, an in-use button 2906 and an always-on button 2912 are displayed. Only one of the in-use button 2906 and the always-on button 2912 can be selected (e.g., set, activated, etc.) at a time.

When the user selects the always-on button 2912 and activates a save 2916 command, an always-join event-based joining tag is sent from the client device, and received by the server, for the directory of contacts. The semantics of the always-join event-based joining tag are such that when a contact is added to the user's list of contacts, the contact is added (such as by the server) to the directory of contacts. As such, when the user exchanges information with a contact, after the always join event-based joining tag is activated, the server (e.g., the network server 232), automatically adds the contact to the directory of contacts for which the tag is active. A cancel command 2914, when activated, causes the tag setting interface 2902 to close without saving any modifications, if any.

When the user selects the in-use button 2906, the user can be presented with additional controls via which the user can set (e.g., select, describe, etc.) additional options (e.g., criteria) for the event-based joining tag. In a first example, a start timestamp 2908 and an end timestamp 2910 controls are presented that allow the user to select and starting date and a time for the event-based joining tag and an ending date and time for the event-based joining tag. As such, the event-based joining tag can be a date-based joining tag. As such, and in the case that the event-based joining tag is a date-based joining tag, the process 2800 can receive a starting date-time (i.e., a start timestamp) for the date-based joining tag and can receive an ending date-time (i.e., an end timestamp) for the date-based joining tag.

Referring again to FIG. 28, at 2806, the process 2806 adds a contact. A contact can be added, for example, as described with respect to FIG. 3.

At 2808, the process 300 determines whether the event-based joining tag is active. An event-based joining tag can be considered active when conditions and/or criteria of the event-based joining tag, taken collectively, can be said to pass (e.g., evaluate to a value that can be considered true). If the event-based tag is active, the process 2800 proceeds to 2812; otherwise the process 2800 ends at 2810. At 2812, the process 2800 adds the contact to the directory of contacts. As such, in response to the event-based joining tag being active, the process 2800 adds the contact to the directory of contacts.

Returning to FIG. 29, when, for example, a contact is added between the starting date and time and the ending date and time of the date-based joining tag, the contact is automatically added, by the server, to the directory of contacts. A directory listing 2930 illustrates that a new contact 2932, whose information was exchanged with the user between Oct. 8, 2018 2:40 PM (as shown in the start timestamp 2908) and Dec. 8, 2018 2:40 PM (as shown by the end timestamp 2910), is added to the directory of contacts named “IO 2018 Conference.” In this illustrative example, the “IO 2018 Conference” is assumed to start on Oct. 8, 2018 2:40 PM and end on Dec. 8, 2018 2:40 PM. As such, whereas the directory listing 2708 of the “IO 2018 Conference” shows only one contact, the updated directory listing (namely, the directory listing 2930) shows two contacts.

While the process 2800 is described with respect to one directory of contacts, it is to be understood that a process according to implementations of this disclosure can add a contact; determine a list of directories of contacts that have active event-based joining tags; and add the contact to each of the list of directories. As described above, an event-based joining tag can be a date-based joining tag, a location-based joining tag, or a combination thereof.

For simplicity of explanation of FIGS. 28-29, only one event-based joining tag is described as being associated to a directory of contacts. However, the implementations according to this disclosure are no so limited. That is, any number of event-based joining tags can be associated with a directory of contacts. At any time that a contact is added to a list of contacts of user, one of more of the event-based joining tags associated with a directory of contacts may be active and one or more of the event-based joining tags associated with the directory of contacts may be inactive. If at least one event-based joining tag is active for a directory of contacts at a time that a contact is added, then the server adds (for example at 2812 of the FIG. 28) the contact to the directory of contacts.

FIG. 30 illustrates additional examples 3000 of user interfaces for setting an event-based joining tag in accordance with implementations of this disclosure. An event-based tag type selector 3004 is illustrated in a tag setting interface 3002. The event-based tag type selector 3004 can be displayed in response to a selection of an in-use button 3006. The in-use button can be similar to the in-use button 2906 of FIG. 29. The event-based tag type selector 3004 displays a list of possible types of event-based joining tag that the user can specify (e.g., configure, set, etc.).

When the user selects one of the event-based tag types, a corresponding UI is displayed. It is to be understood that the user interfaces are mere examples and that other labels, user interface controls, and/or user interface flows and user experiences are possible.

For example, when a date 3008 control is selected by the user, the user can be provided with an interface (not separately shown) whereby the user can select a starting date-time (for example, as described with respect to the start timestamp 2908) and an ending date-time (for example, as described with respect to the end timestamp 2910).

For example, when a city/country/Venue/Landmark 3009 control is selected, the user may be presented with a simple interface where the user can enter the name of a venue, city, state, country, landmark, or a combination thereof. For example, the user may enter “Orlando convention center,” “Orlando, Fla.,” “Florida,” “Seattle,” “Portugal,” and so on. As such, the event-based joining tag can be a location-based joining tag. The location-based joining tag can be an address. The address can include a city name. The address can include a country name.

Accordingly, determining at 2808 of FIG. 28 whether a location-based joining tag is active can include determining a device geolocation of the user device at the time that the contact is added at 2806; determining (e.g., selecting, using, inferring, extracting, etc.) a tag geolocation corresponding to the address of the location-based joining tag; and determining whether the device geolocation is within the tag geolocation.

In an example, in the case where the location-based joining tag is a city, state, or country, then the tag geolocation can be the boundary of the location. In the case where the location-based joining tag can have a corresponding address, such as venue name or a landmark name, then determining whether the device geolocation is within the tag geolocation can mean determining whether the device geolocation is within a threshold distance (e.g., 10 meters, 20 meters, or any other threshold distance) of the address. In some implementations, the threshold distance may be a default value of the server. In other implementations, the threshold distance may be a preference that is set by the user of the user device. In an example, the preference can be set by the user at the time that the user sets the location-based joining tag. A preference that is set by the user can override a default value of the server.

For example, when a map control 3010 is selected, a location selector 3012 can displayed. The user can type an address (e.g., a partial address, etc.) in an address search field 3014. One or more matching results may be displayed in a result list 3016. The user can select one of the search results as the location of the event-based joining tag. When the user selects a matching address, a map 3018 displays the corresponding location. Alternatively, instead of using the address search field 3014, the user can also manipulate the map 3018 to select a desired address. The desired address can correspond to a specific geolocation. As such, the location-based joining tag can be based on a map location. Determining whether the device geolocation is within the tag geolocation can mean determining whether the device geolocation is within a threshold distance (e.g., 10 meters, 20 meters, or any other threshold distance) of the map location, as described above.

For example, when a calendar entry control 3011 is selected, a calendar entry selector 3022 can be displayed. Via the calendar entry selector 3022, the user can select a calendar entry (e.g., a calendar entry 3024) from one of the calendars of the user, which are available via the user device. As is known in the art, a calendar entry can have a start time and an end time. As such, the starting time of the calendar entry can be used as the starting date-time of the event-based joining tag and the ending time of the calendar entry can be used as the ending date-time of the event-based joining tag.

Events (e.g., conferences, symposia, large meetings, and the like) may issue badges to their attendees, who typically wear the badges. In an example, the badges can be used, among other uses, by other attendees to identify the wearer by reading wearer's name on his/her badge. In another example, the badges can be used by an exhibitor at an exhibition hall of the event to keep track (such as for follow up sales and marketing activities) of those event attendees who, for example, stop at (e.g., visit) the exhibitor's booth. The badges can include a machine-readable code. The machine-readable code can be similar a scan code, such as described with respect to FIGS. 8-9. The scan code can embed/encode information about the event attendee (i.e., to whom the badge was issued), the event, other information, or a combination thereof. In an example, the machine-readable code can be a Quick Response (QR) code, a 2-dimensional barcode, or some other machine-readable code.

FIG. 31 illustrates examples 3100 of machine-readable codes that can be used on event badges according to implementations of this disclosure. The examples 3100 includes a badge 3102, a badge 3103, and a QR code 3104.

The badge 3102 is an example of a badge issued for the South by Southwest® (SXSW®) 2019 conference and festival event, as illustrated by an event name 3106. The badge is issued to an attendee named “Ron Czajka,” as illustrated by a name 3108. The badge 3102 includes a machine-readable code, a QR code 3110. In this example, the QR code 3110 embeds the string “R969682{circumflex over ( )}Czajka,” which embeds the last name of the attendee “Ron Czajka.” In an example, the sub-string “R969682” may be used as a unique identifier of the attendee. In an example, the unique id “R969682” may be used to identify (e.g., as an index to) a record of the attendee in a database of the event attendees. In an example, the record of the attendee may include additional information about the attendee such as a phone number, an email address, a company affiliation, and the like. The sub-string “R969682” can have other semantics and/or can be used for other purposes.

The badge 3103 is a badge issued for the TechCrunch Disrupt® event (as indicated by an event name 3112) to “Ron Czajka” (as illustrated by a name 3114). The badge 3103 includes a machine-readable code 3116. In this example, the machine-readable code 3116 cannot be read by a QR reader because it is intentionally damaged, as indicated by a blot 3118.

The QR code 3104 is another example of a machine-readable code that can be included in an event badge. The QR code 3104 encodes the string “Ginko 2019|Ron|Czajka|rjczajka@msn.com.” In this example, the character “|” can be a field separator. The sub-string “Ginko 2019” can be the name of the event for which the badge is issued. The sub-string “Ron” can be the first name of the attendee to whom the badge is issued. The sub-string “Czajka” can be the last name of the attendee to whom the badge is issued. The sub-string “rjczajka@msn.com” can be an email address of the attendee to whom the badge is issued.

In implementations according to this disclosure, machine-readable codes on event badges (e.g., scan codes, QR codes, etc.) can be used to facilitate the exchange of user data or a sub-set of the user data. In an example, a user may attend a plurality of conferences including a first conference and a second conference. At the time of checking into the first conference, the user is given a first badge that includes a first scan code.

The user can (for example, using a camera of a device) scan the first scan code and associate the scanned scan code with one or more first profiles of the user. Similarly, at the time of checking into the second conference, the user is given a second badge that includes a second scan code. The user can (for example, using the camera of a device) scan the second scan code and associate the scanned scan code with one or more second profiles of the user. In an example, the first profiles and the second profiles can be the same profile.

As such, the user can scan different event scan codes (e.g., barcodes) and tie (e.g., associate) the scanned scan codes to the user's account profile whereby the scanned scan codes can be used (i.e., scanned) by other users to detect and exchange contact information with user of the account profile.

In an example, the user can associate the first scan code with a first profile that the user intends to use for sharing data with other attendees of the first conference; and the user can associate the second scan code with a second profile that the user intends to use for sharing data with other attendees of the second conference. As describes above, each of the first profile and the second profile can include a respective subset of the user data. In an example, the first profile and the second profile can include the same subset of the user data. For example, the first profile and the second profile can be a “professional profile.” A professions profile can include a sub-set of the user data that the user is willing (e.g., desires) to share with his/her professional contacts.

FIG. 32 is a process 3200 for data sharing between a first user and a second user in accordance with an implementation of this disclosure. The process 3200 can be implemented, for example, as a software program that can be executed by a system, such as the network server 232 of FIG. 2. The software program can include machine-readable instructions that can be stored in a memory, such as the memory unit 120 of FIG. 1, and that can be executed by a processor, such as the processor 110 of FIG. 1, to cause the system to perform the process 3200.

At 3202, the process 3200 receives a scan code from a first device of the first user.

FIGS. 33A-33B illustrate examples of receiving a scan code in accordance with an implementation of this disclosure. FIGS. 31A-31B illustrate user interfaces, which are further described below, that can be displayed on the first device, which can be a user device such as the user device 202 or one of the one or more user devices 212 of FIG. 2.

FIG. 33A illustrates an example 3310 of receiving a scan code at the time that the user creates (e.g., registers, etc.) a new account profile in the system. Account profile creation or registration can include more steps than those shown in FIG. 33A. However, only steps relevant to receiving the scan code are shown. In an initial step, the user can select a profile to create, as shown in a user interface 3312. The user interface 3312 illustrates that a first profile 3314 that is labeled “Personal profile” and/or a second profile 3316 that is labeled “Work profile” can be created.

As mentioned above, a profile can include a subset of the user data. As also mentioned above, a profile can be selected for sharing with another user. Said another way, if the user selects to share, for example, the “Personal profile” with another user, then the sub-set of the user data associated with the “Personal profile,” and only that subset, can be shared with the other user. A third profile 3317 indicates that any setting selected by the user in subsequent steps will apply to both the first profile 3314 and the second profile 3316. It is to be understood that the first profile 3314 and the second profile 3316 are mere examples and that more, fewer, other profiles, or a combination thereof can be available on the user interface 3312. For example, the user may be able to create additional profiles.

A user interface 3318 illustrates another step of creating the new account profile in the system. For example, the user interface 3318 can be a step in the creation of the second profile 3316. The user interface 3318 includes a control 3319, which enables the user to skip (e.g., omit) adding an event badge (e.g., scan code) to the user's profile.

The user interface 3318 also includes a user control 3320. The user control 3320 enables the user to associate a scan code (such as a scan code of an event) with the user profile. By selecting (e.g., pressing, etc.) the user control 3320, a user interface 3322 can be displayed on the user device. The user interface 3322 can be the same or similar to that described with respect to the application interface display 812 of FIG. 8.

A scan code 3324 illustrates (as indicated by an arrow 3326) that the user has placed the first device over the QR code 3110 of the badge 3102 of FIG. 31. That is, the user interface 3322 illustrates that via a camera of the user device, the QR code 3110 is displayed on a screen of the user device. The badge 3102 of FIG. 31 is reproduced in FIG. 33A for convenience. When the user selects (e.g., presses) a control 3325, the QR code 3110 can be scanned by the user device. Upon scanning the QR code 3110, a user interface 3328 can be presented to the user. Using the user interface 3328, the user can associate a name with the scanned scan code by entering a name in a field 3330. In an example, the name can be the name of the event. For example, the user can enter “SXSW 2019” as the name of the scanned scan code.

Upon the user selecting (e.g., pressing) a control 3332, the scanned scan code can be conveyed (i.e., transmitted, transferred, sent, etc.) to the process 3200 for associating with the user profile. In an example, a message (not shown) indicating to the user that the scan code associated with an event was successfully added to the user's account may be presented to the user. In an example, upon completing the creating of the user profile, the user can be navigated to a home or main screen, such as the application interface display 802 of FIG. 8 or some other main screen.

FIG. 33B illustrates an example 3350 of receiving a scan code subsequent to creating (e.g., registering, etc.) the new account profile in the system. The user can have available a scan code list 3352A. The scan code list 3352A can list all the scan codes that the user has scanned. As shown, the scan code list 3352A includes the scanned scan code “SXSW 2019,” which the user scanned as explained above with respect to the example 3310 of FIG. 33A.

The scan code list 3352A includes an add button 3354. The add button 3354 allows the user to add additional scan codes for additional events. In response to selecting the add button 3354, the user interface 3322 of FIG. 33A can be displayed. As illustrated by an arrow 3353, the user interface 3322 illustrates that the user has placed his/her device over the QR code 3104 of FIG. 31, which is shown in a preview area 3356. That is, the user interface 3322 illustrates that via a camera of the user device, the QR code 3104 is displayed on the screen of the user device. The QR code 3104 of FIG. 31 is reproduced in FIG. 33B for convenience. Upon selecting the control 3325, and the successful scanning of the QR code 3104, the user interface 3328 can be presented (i.e., displayed) to the user, as described above with respect to FIG. 33A.

In the field 3330 (i.e., the name field), the user can enter a name for the event associated with the QR code 3104. In this example, the user has entered “Ginko 2019.” Upon selecting the control 3332, the scanned scan code can be conveyed (i.e., transmitted, transferred, sent, etc.) to the system for associating with the user profile. A scan code list 3352B illustrates that two scan codes are now associated with the user profile. In an example, the scan code list (i.e., the scan code list 3352A or the scan code list 3352B) can be sorted by most recently added. However, more or other sorting options can be available. As is illustrated, in an example, each scan code can be displayed using the name associated with the scanned scan code and the date that the scanned scan code was added by the user.

In some examples, the field 3330 can be pre-populated with a default name, which the user can accept or modify.

In an example, the default name can be extracted from the scan code. For example, as described with respect to the QR code 3104 of FIG. 31, which encodes the string “Ginko 2019|Ron|Czajka|rjczajka@msn.com,” the field 3330 can default to (e.g., be pre-populated with) the name “Ginko 2019.”

In another example, the default name can be identified based at least on one of the location and date of the event. For example, the location of the user device can be used to identify the event. In an example, a database of events and their locations can be accessible to the process 3200. As such, the process 3200 can use the location of the user device and the current date to identify, in the database, the event that corresponds to the event badge. The database of events can be a database that is maintained by the system or can be a publicly query-able database of events, which the process 3200 can query to retrieve the event name.

The scan code list 3352 can include a delete button 3358. The user can use the delete button 3358 to delete scan codes from the system. That is, via the delete button 3358, the user can disassociate one or more scan codes from the user profile. The user can select one or more scan codes from the scan code list 3352 and use the delete button 3358 to delete the selected scan codes. To illustrate, the user can select the scan code named “SXSW 2019” by selecting a radio button 3360 (or a check box or some other toggle control) and pressing the delete button 3358. A confirmation dialog 3362 can be displayed to the user so that the user can confirm the deletion action. In response to the user confirming the action (such as by selecting “Yes”), a request can be transmitted to the system to delete the selected scan code. In response to the user not confirming the action (such as by selection “No”), the selected scan code is not deleted and the user is returned to the scan code list 3352B.

In an example, the scan code may have already been associated with another user account or profile. That is, for example, another user may have already scanned the QR code from an event badge and associated the scanned QR code with a profile of that other user. As such, after the user clicks the control 3332 of FIG. 33B (or FIG. 33A), the process 3200 can determine that the scan code is already associated with a profile, and the process 3200 can cause a message to be displayed to that effect on the user device. In an example, the message can be as shown in a dialog 3368, which states, in part, that the “QR code [just scanned] is already registered” and directs the user to contact technical support.

Returning to FIG. 32, as mentioned above with respect to FIGS. 33A-B, the scanned scan code it transmitted to the system and the system associates the scanned scan code with the user profile. Accordingly, at 3204, the process 3200 can store the scan code in a permanent storage as a stored scan code. For example, the process 3200 can store the scanned scan code in a database as a stored scan code; and, at 3206, the process 3200 can associate the stored scan code with a first profile of the first user. In an example, the first profile can include a sub-set of the user data. In another example, the first profile can be the whole of the user data.

In an example, storing, at 3204, the scan code as the stored scan code can include storing the scanned scan code as an image. In an example, storing the scan code as the stored scan code can include or can mean storing the information that is encoded in the scan code (hereinafter “encoded information”). In an example, the user device can extract (i.e., read from the scan code) the encoded information and transmit the encoded information to the process 3200. In another example, the process 3200 can receive the scanned scan code as an image and extract the encoded information from the received image of the scanned scan code. Accordingly, associating, at 3206, the stored scan code with the first profile of the first user can include associating the encoded information with the first profile of the first user.

In an example, storing the scan code in the permanent storage as the stored scan code can include verifying, prior to the storing the scanned scan code, that the first user is associated with the scan code. Many techniques are possible for verifying that the first user is associated with the scan code.

In an example, the first user can verify that the first user is associated with the scan code by providing a confirmation code that the process 3200 sends to the device of the first user. In an example, after the user presses the control 3332 of FIG. 33A, a dialog 3334 may be displayed on the user device requesting that the user enter a phone number to which a confirmation code is to be sent by the process 3200. The process 3200 can send (or cause to be sent) the confirmation code (such as via a text message, an email, an SMS message, or the like) to the phone number provided by the user. The user can then enter the confirmation code in a dialog 3336. Upon the process 3200 confirming that the confirmation code matches the confirmation code entered by the user, the process 3200 stores the scan code in the permanent storage as the stored scan code. As such, verifying that the first user is associated with the scan code can include identifying contact information for the first user; sending a verification request to the first user; and verifying that the first user is associated with the scan code based on whether a verification response matching the verification request is received from the first user.

In another example of verifying that the first user is associated with the scan code, the process 3200 can match a first subset of information of the scan code with a subset of the first profile. For example, an email address encoded in the scan code can be matched to an email address within the user data. Additionally or instead, a name of the user (i.e., the event attendees) encoded in the scan code can be matched to the name of the user in the user data. Other information that is encoded in the scan code can be matched to data in the user data. In an example, if a match is found, then the scan code can be associated with the user profile. If a match is not found, then the process 3200 can perform the verification as described above with respect to the confirmation code.

In yet another example, an attendee database of attendees may be maintained by the event organizer (e.g., sponsor, etc.). The attendee database can include information regarding the attendees and their associated scan codes. A publicly accessible verification service (e.g., a public API, a web service, or the line) can be provided by the event organizer. In an example, the verification service can receive a scan code (or at least a subset of the information encoded therein) and a user information and return at least a flag (i.e., a verification response) indicating whether the scan code is associated with the user information. As such, the process 3200 can use the verification service to verify that the scan code is associated with at least a subset of the user data (e.g., a name, an email address, a phone number, other information, or a combination thereof) that is extracted from the user data of the user. In an example, the system executing the process 3200 can be configured to associate events (e.g., event names, locations, and dates) with their respective verification services.

As such, in an example, verifying that the first user is associated with the scan code can include identifying a verification service associated with the event; sending a verification request to the verification service using at least a subset of the first profile; verifying that the first user is associated with the scan code based on a verification response received from the verification service.

At 3208, the process 3200 receives, from a second device of the second user, an indication that the second user scanned the scan code. That is, the second user scanned the scan code that is on the badge as opposed to scanning the stored scan code. As such, the second user did not scan the stored scan code from the device of the first user, as described with respect to FIGS. 8-9. In an example, the indication can include an image of the scan code, the information encoded in the scan code, some other indication, or a combination thereof.

In a illustrative example, the second user and the first user may strike up a conversation at the event and agree to share contact information. The second user can scan, using the camera of the device of the second user, the scan code that is on the event badge of the first user. As is typically the case, the first user may be wearing the badge around his or her neck. In another illustrative example, the first user may stop at the booth of an exhibitor at the exhibition hall of the event to learn about the products or services of the exhibitor. A marketing person (i.e., the second user) at the booth may ask the first user whether the marketing person can connect with the first user for follow up discussions. The marketing person can then scan the scan code off the badge of the first user.

FIG. 34 illustrates an example 3400 of scanning an event badge in accordance with an implementation of this disclosure. The scenario described with respect to the example 3400 is similar to that described with respect to FIG. 8. Using the device of the second user, the application interface display 812 of FIG. 8 can be used by the second user to scan a machine-readable code (e.g., a scan code) off the event badge of the first user. In the example 3400, the event badge of the first user is the badge 3102 of FIG. 31. When the second user executes the scan using the camera icon 816, an indication can be transmitted from the second device to the process 3200. The indication can be a request that is sent from the second device to the process 3200 indicating to send a contact request to the first user.

At 3210, the process 3200 identifies, for the first user, the second user as a potential contact. Upon receiving the indication at 3208, the process 3200 can identify (e.g., locate) the first user. More specifically, the process 3200 can determine whether the scan code is associated with any user profile. That is, in an example, the process 3200 can use the scan code received in the indication to identify a user associated with the scan code. In another example, the process 3200 can use the encoded information that is received in the indication to identify a user associated with the scan code. In yet another example, the process 3200 receives the scan code in the indication, identifies the encoded information in the scan code, and uses the encoded information to identify a user associated with the scan code.

At 3212, the process 3200 sends, to the first user, a first request to share first user data of the first user with the second user. That is, if a user (e.g., the first user) associated with the scan code is identified, then the process 3200 identifies the second user as a potential contact for the first user. An application interface display 3402, which is similar to the application interface display 822 of FIG. 8, can be generated in response to receiving the indication, which displays the selectable user data screen from which the first user may input whether to share all user data, share some user data, or chat only, in a manner as shown and described herein with respect to FIG. 6. In an example, via the application interface display 3402, the first user can select whether to share the sub-set of user data that is associated with the scan code or to only chat. As such, at 3214, the process 3200 receives, from the first user, a response to the first request to share the first user data of the first user with the second user.

In an example, and as described above, the response to the first request can include a rejection by the first user to establish the second user as a contact. In an example, and as also described above, the response to the first request can include an acceptance, by the first user, to establish the second user as a contact of the first user.

In an example, a user associated with the scan code may not identified. That is, the process 3200 does not identify that a user (e.g., the first user) scanned the scan code and associated the scan code with a user profile, as described with respect to at least one of FIG. 33A or FIG. 33B. One possible reason for not identifying a user associated with the scan code may be that the user does not have a user profile in the system. As such, a message 3404 can be displayed for the second user. The message 3404 identifies to the second user that the QR code 3110 is not found and asks the second user whether the process 3200 should sent an invitation to the first user to create a user account.

In response to the second user selecting a yes button 3406, the second user can send an invitation, such as shown in an invitation 3408, to create a user account. The process 3200 can generate the contact of the invitation 3408 and the second user selects a contact mode of the first user to send the invitation to. The contact mode can be an email address of the first user, a phone number of the first user, or some other contact mode of the first user. In an example, the second user can verbally ask the first user for a contact mode. In another example, the second user may already have the contact mode of the first user in a contacts list of the second user.

In an example, and as described above, the first user may have created a directory of contacts for the event and may have associated an event-based joining tag with the directory. As such, upon the second user scanning the badge of the first user, the second user can be automatically added the directory of contacts.

In an example, the process 3200 can include receiving a second request from the first user to identify contacts of the first user established using the scan code; and providing a list of the contacts of the first user established using the scan code. That is, the first user can request that the process 3200 identify all the other users who became contacts of the first user by scanning the scan code off the event badge of the user. That is, the first user can, for example, issue a query essentially stating, “Show a list of the contacts I established using the scan code named ‘Ginko 2019’.” The process 3200 responds by displaying the list of those contacts.

In an example of 3202 of the process 3200, the scan code can be a default scan code that is generated by the system when the user creates a new account profile. As such, receiving a scan code from a first device of the user can mean generating a scan code in response to receiving a request to create a new account profile from the first device of the user. As such, the scan code can be as described with respect to FIG. 9.

In an example, a date range can be associated with a stored scan code. The date range can be a starting date and an ending date associated with the event. In an example, the user can provide the date range at the time of scanning the scan code to associate it with a user profile. In an example, the process 3200 can automatically disassociate the stored scan code from the user profile on or after the expiration date. As such, the process 3200 can include receiving an expiration date associated with the scan code; and automatically disassociating the stored scan code from the first profile of the first user on or after the expiration date. Disassociating the stored scan code from the first profile can mean deleting the stored scan code.

For simplicity of explanation, the processes 300, 2500, 2600, 2800, and 3200 are depicted and described as a series of steps. However, steps in accordance with this disclosure can occur in various orders, concurrently, and/or iteratively. Additionally, other steps or operations not presented and described herein may be used.

Furthermore, not all illustrated steps or operations may be required to implement a technique in accordance with the disclosed subject matter. For example, some implementations of the process 2500 may not include the one or more of the sequence of steps 2506-2510, the sequence of steps 2512-2514, and/or the sequence of steps 2516-2518. For example, some implementations of the process 2600 may not include one of steps 2604 or 2606.

While the invention has been described in connection with certain embodiments, it is to be understood that the invention is not to be limited to the disclosed embodiments but, on the contrary, is intended to cover various modifications and equivalent arrangements included within the scope of the appended claims, which scope is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structures as is permitted under the law. 

What is claimed is:
 1. A system for data sharing between a first user and a second user, the system comprising: a memory; and a processor, the processor configured to execute instructions stored in the memory to: receive a scan code from a first device of the first user; verify, prior to storing the scan code as a stored scan code, that the first user is associated with the scan code; store the scan code in a permanent storage as the stored scan code; associate the stored scan code with a first profile of the first user, the first profile comprising user data; receive, from a second device of the second user, an indication that the second user scanned the scan code using a camera of the second device, wherein the second user did not scan the stored scan code; identify, for the first user, the second user as a potential contact; send, to the first user, a first request to share the user data of the first user with the second user; and receive, from the first user, a response to the first request to share the user data of the first user with the second user.
 2. The system of claim 1, wherein the response to the first request comprises a rejection by the first user to establish the second user as a contact.
 3. The system of claim 1, wherein the response to the first request comprises an acceptance, by the first user, to establish the second user as a contact of the first user.
 4. The system of claim 1, wherein to verify that the first user is associated with the scan code comprises to: match a first subset of information of the scan code with a subset of the first profile.
 5. The system of claim 1, wherein to verify that the first user is associated with the scan code comprises to: identify contact information for the first user; send a verification request to the first user; and verify that the first user is associated with the scan code based on whether a verification response matching the verification request is received from the first user.
 6. The system of claim 1, wherein to verify that the first user is associated with the scan code comprises to: identify a verification service associated with an event; send a verification request to the verification service using at least a subset of the first profile; and verify that the first user is associated with the scan code based on a verification response received from the verification service.
 7. The system of claim 1, wherein the instructions further comprise instructions to: receive a second request from the first user to identify contacts of the first user established using the scan code; and provide a list of the contacts of the first user established using the scan code.
 8. The system of claim 1, wherein to receive the scan code from the first device of the first user comprises to: receive an expiration date associated with the scan code; and the instructions further comprising instructions to: automatically disassociate the stored scan code from the first profile of the first user on or after the expiration date.
 9. A method for data sharing between a first user and a second user, the method comprising: receiving a scan code from a first device of the first user; verifying that the first user is associated with the scan code; responsive to the verifying, storing the scan code in a permanent storage as a stored scan code; associating the stored scan code with a first profile of the first user, the first profile comprising user data; receiving, from a second device of the second user, an indication that the second user scanned the scan code using a scanning sensor of the second device, wherein the second user did not scan the stored scan code; identifying, for the first user, the second user as a potential contact; sending, to the first user, a first request to share the user data of the first user with the second user; receiving, from the first user, a response to the first request to share the user data of the first user with the second user; and establishing the second user as a contact of the first user.
 10. The method of claim 9, wherein verifying that the first user is associated with the scan code comprising: matching a first subset of information of the scan code with a subset of the first profile.
 11. The method of claim 9, wherein verifying that the first user is associated with the scan code comprising: identifying contact information for the first user; sending a verification request to the first user; and verifying that the first user is associated with the scan code based on whether a verification response matching the verification request is received from the first user.
 12. The method of claim 9, wherein verifying that the first user is associated with the scan code comprising: identifying a verification service associated with an event; sending a verification request to the verification service using at least a subset of the first profile; and verifying that the first user is associated with the scan code based on a verification response received from the verification service.
 13. The method of claim 9, further comprising: receiving a second request from the first user to identify contacts of the first user established using the scan code; and providing a list of the contacts of the first user established using the scan code.
 14. The method of claim 9, wherein receiving the scan code from the first device of the first user comprising: receiving an expiration date associated with the scan code; and the method further comprising: automatically disassociating the stored scan code from the first profile of the first user on or after the expiration date.
 15. A system for data sharing between a first user and a second user, the system comprising: a memory; and a processor, the processor configured to execute instructions stored in the memory to: receive a scan code from a first device of the first user; verify that the first user is associated with the scan code; responsive to the verifying that the first user is associated with the scan code, store the scan code in a permanent storage as a stored scan code; associate the stored scan code with a first profile of the first user, the first profile comprising user data; receive, from a second device of the second user, an indication that the second user scanned the scan code using the second device, wherein the second user did not scan the stored scan code; in response to determining that a profile of the first user is public, enable the second user to access the profile of the first user; and in response to determining that the profile of the first user is not public, execute instructions to: send, to the first user, a first request to share the user data of the first user with the second user; and receive, from the first user, a response to the first request to share the user data of the first user with the second user. 